Importing CCTs

It is possible to import an archive containing CCT(s) and their associated files such as Script and Stub directories and files. This can then be used to aid support when CCT updates are needed.

CCTs are stored in several places and using the import (and export) commands will help to ensure these areas remain consistent. Using the ’-C’ (or --cct-location) specifies where the CCT will be imported to. Values are:

  • INSTALL: The CCT installation directory, eg

    /home/bill/Helix-QAC-<version>/config/cct

    or

    C:\Perforce\Helix-QAC-<version>\config\cct
  • LOCAL: The CCT directory in the local user data location, eg

    /home/bill/.config/Perforce/Helix-QAC-<version>/config/cct

    or

    C:\%LOCALAPPDATA%\Perforce\Helix-QAC-<version>\config\cct
  • PROJECT: The CCT directory of a project, eg

    /home/bill/sample/configs/Initial/config/cct

    or

    C:\sample\configs\Initial\config\cct
  • ALL: Effectively an alias for INSTALL, LOCAL, and PROJECT. It allows a CCT to fully replace and existing CCT.
  • USER: Any file or directory specified by the user

The import-file specifies the name of the input file.

If you try to import to INSTALL either directly or indirectly (by using ALL) you must have the appropriate permissions to do so.
When importing to a project you can only import the same number and names of CCTs i.e. you cannot try to change to a different CCT by using import.